Crowd sourced rtt-based positioning

ABSTRACT

In various embodiments, crowd sourcing techniques are provided to enable RTT-based positioning of UE. To address issues of discovering which beacons (e.g., Wi-Fi APs, cellular base stations, BLE transmitters, etc.) support measurement of RTT (e.g., according to IEEE 802.11mc, 3GPP Release 16, etc.), beacon RTT capabilities may be crowd-sourced from UE and maintained by a cloud-based location platform in a beacon database (or more specifically, a RTT database portion thereof). To address the issue of determining physical antenna positions, RTT measurements may be crowd-sourced from UE for those beacons that are RTT capable, and used by a trilateration algorithm (e.g., a WLS multilateration algorithm) to determine physical antenna positions, which also may be maintained in the beacon database. Accuracy of the trilateration may be enhanced by obtaining raw GNSS measurements (e.g., pseudoranges) from the UE, and performing a cloud-based RTK GNSS position fix for the UE.

BACKGROUND Technical Field

The present disclosure relates generally to user equipment (UE)positioning, and more specifically to crowd sourcing techniques toenable round-trip time (RTT)-based positioning of UE.

Background Information

Determining UE position is becoming increasing important for trackingusers, managing profiles, providing location-based services, and othertasks. A number of techniques for determining UE position have involvedreceived signal strengths (RSS) measurements. For example, atriangulation of RSS measurements of signals received at the UE frommultiple beacons (e.g., Wi-Fi access points (APs), cellular basestations, Bluetooth Low-Energy (BLE) transmitters, etc.) may beperformed. However, RSS-based techniques may have difficulty determininghigh precision UE positions.

Improved precision may be possible by utilizing RTT measurements in thedetermination of UE position. In general, RTT is the time that passesbetween the transmission of an initiating signal and the reception of acorresponding response signal. Time-of-flight (ToF) may be obtained bysubtracting turnaround time from RTT, and dividing the result by two.From ToF a distance (range) between the UE and the beacon may be readilydetermined. Based on the distance to multiple beacons, the position ofthe UE may be determined, for example via trilateration.

Various new protocols, such as the fine timing measurement (FTM)protocol introduced in the Institute of Electrical and ElectronicsEngineers (IEEE) 802.11mc standard, and the protocols introduced in the3rd Generation Partnership Project (3GPP) Release 16 technicalspecification (TS) series 37 and 38, enable highly accurate measurementof RTT. With a Wi-Fi AP that supports FTM protocol, RTT may be measuredfrom timestamps that are captured at departure and arrival of FTM framesand their respective acknowledgements. With a cellular base station thatsupports that supports 3GPP Release 16, a specific sub-type of RTTreferred to as multi-RTT may be measured.

UE may use various mechanisms to discover which beacons supportmeasurement of RTT. For example, FTM protocol provides two mechanismsfor discovering which Wi-Fi APs support RTT measurements: advertisementframes and range requests. With advertisement frames, a Wi-Fi APperiodically broadcasts a frame to advertise to UE its RTT capabilities.With range requests, UE establish a peer link to the Wi-Fi AP andattempt to have the Wi-Fi AP measure RTT with it, sending a requestframe and waiting to receive a burst of response frames, to which itresponds with acknowledgements. With either advertisement frames orrange requests, an extended capabilities element (e.g., included in anadvertisement frame or in an initial response frame) may provideinformation regarding scheduling and operational details of the FTMsession, such as burst duration, FTM frames per burst, bandwidth,minimum time between consecutive FTM frames, and the like. Likewise,3GPP Release 16 provides its own mechanisms to discover which cellularbase stations support RTT.

While using RTT may improve precision of UE position determination, anumber of obstacles have hindered the widespread deployment of RTT-basedpositioning. First, it is often error prone and operationally expensive(in terms of time, processor cycles, memory space, network bandwidth andpower) to determine which beacons support measurement of RTT. Somebeacons may simply lack the functionality to support measurement of RTT(e.g., they only support older protocols and standards). Other beaconsmay include the functionality (e.g., their chipset supports theapplicable protocols and standards) but they do not advertise their RTTcapabilities for various reasons. For example, with FTM protocol, only afraction of deployed Wi-Fi APs currently support the IEEE 802.11mcstandard and FTM protocol. Of that fraction, some Wi-Fi APs do notadvertise their capabilities to support FTM protocol. UE interested inlearning which Wi-Fi APs support FTM protocol typically have twosub-optimal options: they can rely on advertisements, and thereby missWi-Fi APs that do not advertise their capabilities, or they canestablish peer links and send request frames to each nearby Wi-Fi AP,and thereby consume significant time, processor cycles, memory space,network bandwidth and power. In a dense urban area, there may be tens oreven hundreds of nearby Wi-Fi APs such that having every UE establishpeer links and send request frames to every nearby Wi-Fi AP is simply betoo operationally expensive to be practical.

Second, it may be difficult to determine physical antenna positions to alevel of precision that can fully realize the benefits for RTT-basedpositioning. RTT-based positioning typically requires highly accuratephysical antenna positions (e.g., within 1 meter) to realized its fullbenefits. One way to obtain such physical antenna positions is bydedicated surveys. For example, a Wi-Fi survey system or vehicleincluding high-precession hardware may traverse a site and map physicalantenna positions of Wi-Fi APs. While the physical antenna positionsdetermined by such an approach may be accurate, it is extremely timeconsuming and expensive. An alternative approach is to approximatephysical antenna positions based on coverage areas of beacons, which mayalready be known from other positioning techniques. For example, aphysical antennal position of a Wi-Fi AP may be approximated as thecentroid of coverage of the Wi-Fi AP. However, such an approach isgenerally not very accurate. The centroid of coverage often divergesfrom the physical antenna position due to signal propagation biases,observational biases and other factors.

Accordingly, there is a need for improved techniques that can addressthese and/or other issues that have hindered widespread deployment ofRTT-based positioning of UE.

SUMMARY

In various embodiments, crowd sourcing techniques are provided to enableRTT-based positioning of UE. To address issues of discovering whichbeacons (e.g., Wi-Fi APs, cellular base stations, BLE transmitters,etc.) support measurement of RTT (e.g., according to IEEE 802.11mc, 3GPPRelease 16, etc.), beacon RTT capabilities may be crowd-sourced from UEand maintained by a cloud-based location platform in a beacon database(or more specifically, a RTT database portion thereof). To address theissue of determining physical antenna positions, RTT measurements may becrowd-sourced from UE for those beacons that are RTT capable, and usedby a trilateration algorithm (e.g., a weighted least square (WLS)multilateration algorithm) to determine physical antenna positions,which also may be maintained in the beacon database. Accuracy of thetrilateration may be enhanced by obtaining raw global navigationsatellite system (GNSS) measurements (e.g., pseudoranges) from the UE,and performing a cloud-based Real Time Kinematic (RTK) GNSS position fixfor the UE.

In one embodiment, a positioning client on UE is used to crowd-sourcebeacon RTT capabilities. The UE uses a wireless network interface toscan for beacons within range of the UE. The UE accesses informationfrom a beacon database maintained by a cloud-based location platform todetermine whether RTT capabilities are known for each beacon withinrange. For one or more beacons having unknown RTT capabilities, the UEsends a range request to attempt to have the beacon measure RTT, andbased thereon assigns the beacon a RTT measurement status that indicatesthe beacon's RTT capabilities. The UE then uploads at least the RTTmeasurement status to the cloud-based location platform to update thebeacon database. In such embodiment, the UE both consumes informationregarding RTT capabilities of beacons from the beacon database, andcontributes information regarding RTT capabilities of beacons to thebeacon database.

In another embodiment, a cloud-based location platform is used tocrowd-source beacon RTT capabilities. The cloud-based location platformprovides a plurality of UE with information regarding RTT capabilitiesof beacons from a beacon database. At least one of the beacons initiallyhas unknown RTT capabilities. The cloud-based location platform laterreceives RTT information including at least RTT measurement status fromone or more of the plurality UE that have attempted to measure RTT withthe beacon initially having unknown RTT capabilities. RTT capabilitiesof the beacon are determined based on the received RTT measurementstatus and the beacon database is updated to include informationindicating the RTT capabilities of the beacon. In such embodiment, theoperation permits UE to both consume information regarding RTTcapabilities of beacons from the beacon database, and contributeinformation regarding RTT capabilities of beacons to the beacondatabase.

In yet another embodiment, a cloud-based location platform determinesbeacon position, or more specifically beacon physical antenna position,based on crowd-sourced data. The cloud-based location platform receivesobservations from a plurality of UE that have observed a beacon, theobservations including at least a determined position of the UE and aRTT measurement for the UE by the beacon. The cloud-based locationplatform uses a trilateration algorithm to determine physical antennaposition of the beacon based on the determined position and the RTTmeasurement for each of the plurality of UE. The cloud-based locationplatform updates the beacon database to include the determined physicalantenna position of the beacon and provides the physical antennaposition of the beacon to one or more of the plurality of UE. In suchembodiment, the operation permits UE to both contribute information usedto determine physical antenna position of the beacon to build the beacondatabase and consume physical antenna position of the beacon from thebeacon database.

In still another embodiment, a cloud-based location platform determinesbeacon position, or more specifically beacon physical antenna position,based on crowd-sourced data, where accuracy of such determination isimproved using a cloud-based RTK GNSS position fix for UE position. Thecloud-based location platform receives information from a plurality UEthat have observed a beacon including at least raw GNSS measurements forthe UE and a RTT measurement for the UE. It also obtains RTK correctioninformation from a correction service for the raw GNSS measurements. Thecloud-based location platform determines a corrected GNSS position fixfor each UE using the raw GNSS measurements and the RTK correctioninformation. Thereafter, the cloud-based location platform use atrilateration algorithm to determine position of the beacon based on thecorrected GNSS position fix and the RTT measurements, and updates abeacon database to include the determine physical antenna position ofthe beacon. It then provides the physical antenna position of the beaconto one or more of the plurality of UE.

It should be understood that the embodiments discussed in this Summarymay include a variety of other features, including other featuresdiscussed below, and variations thereof. Further a variety of otherembodiments may be utilized involving various combinations of thefeatures discussed herein and below, and variations thereof. ThisSummary is intended simply as a brief introduction to the reader, anddoes not imply that the specific features mentioned herein are all thefeatures of the invention, or are essential features of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The description below refers to the accompanying drawings, of which:

FIG. 1 is a block diagram of an example architecture in which techniquesto enable RT-based positioning of UE may be deployed;

FIG. 2 is a flow diagram detailing example operations performed underdirection of the positioning client on UE to crowd-source beacon RTTcapabilities;

FIG. 3 is a flow diagram detailing example operations performed by thecloud-based location platform to crowd-source beacon RTT capabilities;

FIG. 4 is a flow diagram detailing example operations performed by thecloud-based location platform to determine beacon position, or morespecifically beacon physical antenna position, using RTT measurementscrowd-sourced from UE;

FIG. 5 is a diagram of an example arrangement of UE illustrating HPE andits use as an indicia of accuracy of a position determination;

FIG. 6 is a flow diagram detailing example operations performed by thecloud-based location platform in an “off-board” implementation todetermine beacon position, or more specifically beacon physical antennaposition, using a cloud-based RTK GNSS position fix; and

FIG. 7 is a flow diagram detailing example operations performed by apositioning client on a UE to implement a hybrid RTT-based positioningalgorithm to determine UE position.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an example architecture 100 in whichtechniques to enable RTT-based positioning of UE may be deployed. Asused herein, the term “user equipment” or “UE” refers to a mobiledevice, Machine-to-Machine (M2M) device or Internet of Things (IoT)device operated by an end user. Examples of UE 110 include smartphones,smartwatches, computers, cameras, and sensors operated by end users,among others. Likewise, as used herein the term “beacon” refers to adevice having a fixed position that exchanges signals which may be usedto determine a position of the UE. Examples of beacons 140 include Wi-FiAPs, cellular base stations, BLE transmitters, among other devices.Further, as used herein the term “RTT capabilities” refers the abilityof a beacon to measure RTT (or sub types thereof, such as multi-RTT) ingeneral, and provide measured RTT to other devices. RTT capabilities maybe according to FTM protocol of the IEEE 802.11mc standard, 3GPP Release16 TS series 37 and 38, or other protocols and standards. Still further,as used herein the term “RTT measurement status” refers to the abilityof a beacon to perform a specific measure RTT measurement. RTTmeasurement status may be according to FTM protocol of the IEEE 802.11mcstandard, 3GPP Release 16 TS series 37 and 38, or other protocols andstandards.

UE 110 typically includes a central processor unit (CPU) 115, storage120 (e.g., volatile and non-volatile memory) that maintains applicationsoftware including a positioning client 122, one or more wirelessnetwork interfaces 125 (e.g., a Wi-Fi interface operating according to aIEEE 802.11 standard, a cellular radio operating according to 3GPPRelease 16 TS series 37 and 38, and/or another type of wirelessinterface), a GNSS receiver 130 that receives satellite signals, among anumber of other components.

The positioning client 122 typically utilizes a wireless networkinterface to scan for beacons 140 (e.g., Wi-Fi APs, cellular basestations, BLE transmitters, etc.) within range of the UE 110 and todetermine characteristics thereof. These characteristics may be used inconjunction with a local copy of beacon information to determine aposition of the UE 110. Likewise, the positioning client 122 may utilizethe GNSS receiver 130 to capture raw GNSS measurements (e.g.,pseudoranges) from satellites. The raw GNSS measurements may also beused to determine a position of the UE (i.e. a GNSS position fix).

The UE 110 may communicate via a Wi-Fi or cellular data communicationpath to the Internet 150 and a cloud-based location platform 160. Amongother functions, the location platform 160 typically maintains thebeacon database 170. A portion of the beacon database 170 may bedesignated as a RTT database 175, and relate an identifier of a beacon(e.g., a media access control (MAC) address, cell identifier (ID), etc.)to various RTT-related information, such as the beacon's RTTcapabilities (e.g., RTT capable, RTT incapable or having unknown RTTcapabilities), a RTT bias, a beacon physical antenna position, aposition uncertainty, etc. Portions of the beacon database (includingthe RTT database 175) that cover a specific geographic area (e.g.,tiles) may be downloaded by the positioning client 122 to the UE 110 foruse as the local copy. Further, information derived from scans performedby the UE 110 (e.g., a determined position of the UE, beacon identities,RTT measurement status, RTT measurements, etc.) may be periodicallyuploaded to the cloud-based location platform 160 which uses theinformation to update to the beacon database 170 (including the RTTdatabase 175).

FIG. 2 is a flow diagram detailing example operations 200 performedunder direction of the positioning client 122 on UE 110 to crowd-sourcebeacon RTT capabilities. At step 210, the positioning client 122 uses awireless network interface 125 of the UE 110 to perform a scan todiscover beacons 140 within range of the UE. The scan may be an activescan (e.g., in response to a present request to compute UE position foran application executing on the UE 110), or a background scan (e.g., abackground operation absent any present request to determine position ofthe UE). At step 215, for implementations that utilize local copies ofportions of the beacon database 170 that cover geographic areas (e.g.tiles), the positioning client 122 checks whether the UE 110 is storinga local copy of a portion of the beacon database 170 (e.g., a tile) thatcovers the geographic area including the present position of the UE 110.If not, at step 220, it downloads a local copy (e.g., tile) from thecloud-based location platform 160. This may occur each time the UE is ina new geographic area or when previously downloaded local copies (e.g.,tiles) have aged out. It should be understood that some implementationsmay not use local copies (e.g., tiles), and in such case steps 215-220may be omitted.

At step 225, the positioning client 122 loops through each beacon 140within range of the UE 110, and, at step 230, checks to determinewhether RTT capabilities are already known. In an embodiment that uselocal copies (e.g., tiles) this may involve checking the beacon'sidentity in the local copy (e.g., tile). Alternatively, this may involvequerying the cloud-based location platform 160. RTT capabilities mayhave a number of states, including RTT capable (i.e. a state indicatingsome other UE has been able to have the beacon measure RTT in the past),RTT incapable (i.e. a state indicating other UE have tried to have thebeacon measure RTT in the past but none have been able to) or havingunknown RTT capabilities (i.e. a state indicating no UE has triedmeasuring RTT in the past). At step 235, for each beacon 140 withinrange of the UE 110 indicated to be RTT capable or having unknown RTTcapabilities, the positioning client 122 adds the beacon to a range list(i.e. a list of identifiers (e.g., MAC addresses, cell IDs, etc.)designated to receive range requests.

At step 240, the positioning client 122 loops through each beacon 140 onthe range list, and at step 245 causes the wireless network interface125 to send a range request (e.g., a FTM protocol range requestaccording to the IEEE 802.11mc standard, or a request according toanother standard) to attempt to have the beacon 140 measure RTT with it.At step 250, the positioning client 122 assigns the beacon 140 a RTTmeasurement status that indicates the beacon's RTT capabilities. Theassigned RTT measurement status may indicate the beacon is RTT capable(i.e. the beacon was able to measure and return RTT), RTT incapable(i.e. the beacon was not able to measure and return RTT), or RTTout-of-range (i.e. the beacon was not able to measure RTT, but thebeacon returned an out-of-range indication, such that the beacon may beable to measure and return RTT if the range were less).

At step 255, the positioning client 122 determines position of the UE110. The determination may be based on GNSS such that the determinedposition is a GNSS position fix. Alternatively, or additionally, thedetermination may utilize RT-based positioning. Such RTT-basedpositioning may utilize a hybrid positioning algorithm that combines aRT-based WLS positioning algorithm and an Extended Kalman positioningalgorithm, as discussed in more detail below. A position confidence(e.g., an estimated horizontal position error (HPE)) may be calculatedfor the determined position of the UE 110.

At step 260, in implementations that utilize caching, the positioningclient 122 adds RTT information for the beacons within range to a localcache of the positioning client 122 on the UE 110. The RTT informationmay include the determined position of the UE (and in some casesposition confidence), and for each beacon the identifier of the beacon(e.g., MAC address, cell ID, etc.), the RTT measurement status (e.g.,RTT capable, RTT incapable, or RTT out-of-range), and, if available, aRTT measurement. At step 265, the positioning client 122 determineswhether a cache upload trigger has been reached. The trigger may be thelocal cache becoming full, a certain amount of time expiring, or someother criteria that is periodically met. If the trigger has beenreached, at step 270, the positioning client 122 uploads contents of thelocal cache to the cloud-based location platform 160 for inclusion in anupdate to the beacon database 170 (or more specifically, the RTTdatabase 175 thereof). It should be understood that some implementationsmay not use caching, and in such case steps 260-265 may be omitted andthe upload of step 270 commenced immediately when there is new RTTinformation for the beacons. Finally, at optional step 275, thepositioning client 122 reports the determined position of the UE toother application software (e.g., if the original scan was an activescan).

FIG. 3 is a flow diagram detailing example operations 300 performed bythe cloud-based location platform 160 to crowd-source beacon RTTcapabilities. The operations may aggregate information discovered by alarge number of UE 110 to build the beacon database 170 (and the RTTdatabase 175 thereof). At step 310, the cloud-based location platform160 batches received RTT information from UE 110. As discussed above,the RTT information may include the determined position of the UE, andfor each beacon 140 within range of the EU, the identifier of the beacon(e.g., MAC address, cell ID, etc.), the RTT measurement status (e.g.,RTT capable, RTT incapable, or RTT out-of-range), and, if available, theRTT measurement.

At step 320, in implementations that batch updates, the cloud-basedlocation platform 160 determines a batch period has been reached. Thebatch period may be a period of time (e.g., once a month), or a non-timebased trigger, at which RTT capabilities of beacons 140 in the beacondatabase 170 are updated. It should be understood that someimplementations may not use batching, in which case step 320 may beomitted and an operations commenced in real-time.

At step 330, the cloud-based location platform 160 loops through eachbeacon 140 in the batch, iterating through identifiers (e.g., MACaddress, cell ID, etc.) and examining an aggregate of the RTTinformation for the beacon. At step 340, the cloud-based locationplatform 160 determines RTT capabilities of the beacon 140 based on theRTT measurement status in the RTT information for the beacon. The beacon140 may be marked RTT capable if the RTT measurement status from atleast one UE 110 indicates it is RTT capable. The beacon 140 may bemarked RTT incapable if the RTT measurement status from all of the UE110 indicates it is RTT incapable. The beacon 140 may be marked ashaving unknown RTT capabilities if the RTT measurement status from atleast one UE 110 indicates the beacon is RTT out-of-range (but the RTTmeasurement status of no UE 110 indicates the UE is RTT capable).

At step 350, the cloud-based location platform 160 determines if the RTTcapabilities of the beacon 140 indicate it is RTT capable. If not,execution loops to examine the next beacon. If so, execution proceeds tostep 360, where the cloud-based location platform 160 estimates an RTTbias for the beacon 140 that measures an expected offset/error in RTTmeasurements by the beacon. The RTT bias may be estimated using varioustechniques. For example, a delta may be computed between aRTT-determined distance between the UE 110 and the beacon 140 and aposition-fix-determined distance between the UE and the beacon. If thedelta is substantially the same across a number of (e.g., all) UE 110that have observed the beacon 140, the delta may be used as the RTT biasof the beacon. Also, the cloud-based location platform 160 may determineother beacons 140 that share a common organization identifier (e.g.,organizationally unique identifier (OUI)) with the beacon. If a numberof these other beacons share substantially the same RTT bias, this RTTbias may be assumed for the present beacon. This may permit theestimation of RTT bias in situations where delta computations are notpossible.

At step 370, the cloud-based location platform 160 determines whetherdistance (range) between the UE 110 and the beacon 140 computed based onRTT is reasonable. For example, it may be determined if the distance isconsistent with distance between the position of the UE 110 using othertechniques (e.g., a GNSS position fix) and the beacon position in thebeacon database 170. If the RTT-based distance is not reasonable, theRTT capabilities of the beacon 140 are updated (e.g., to mark the beaconas RTT incapable).

At step 380, the cloud-based location platform 160 determines physicalantenna position of the beacon 140. The determination uses atrilateration algorithm (e.g., a WLS multilateration algorithm) thattakes RTT measurements from multiple UE. Details of example operationsto determine physical antenna position are discussed below.

When execution is done looping through each of the beacons, at step 390,the cloud-based location platform 160 updates the beacon database 170(or more specifically the RTT database 175 thereof) to include the newRTT capabilities. Thereafter, in implementations that utilize localcopies (e.g., tiles), portions of the updated beacon database 170 may beprovided back to UE 110 to inform them of RTT capabilities of beacons,so they can perform RTT-based positioning.

FIG. 4 is a flow diagram detailing example operations 400 performed bythe cloud-based location platform 160 to determine beacon position, ormore specifically beacon physical antenna position, using RTTmeasurements crowd-sourced from UE 110. At step 410, the cloud-basedlocation platform 160 receives observations from UE 110 of RTT capablebeacons 140. The observations may include the determined position of theUE (e.g., a GNSS position fix) and a position confidence of thedetermined position (e.g., an HPE of the GNSS position fix), anidentifier of the beacon (e.g., MAC address, cell ID, etc.) and RTTinformation. The RTT information may include a RTT measurement, a RTTmeasurement uncertainty, a signal strength associated with the RTTmeasurement, a bandwidth associated with the RTT measurement, as well asother RTT-related data. At step 420, the cloud-based location platform160 aggregates observations for a given beacon 140. At step 430, thecloud-based location platform 160 filters out observations based on acomparison of the position confidence of the determined position of theUE (e.g., the HPE of the GNSS position fix) and a threshold. Preferably,the threshold is set to remove only observations with very poor positionconfidence (e.g., observations with very large HPE). Moderatelyconfident observations may be addressed by weighting in subsequentoperations.

At step 440, the cloud-based location platform uses a trilaterationalgorithm to determine beacon position, or more specifically beaconphysical antenna position, based on the aggregated observations from theUE 110. The trilateration algorithm may be a WLS multilaterationalgorithm in which the weight is a function of confidence of thedetermined position of the UE (e.g., the HPE of the GNSS position fix),RTT measurement uncertainty, a RTT-determined range (e.g., withmeasurements from longer range being considered less reliable), signalstrength associated with the RTT measurement, a number of RTTmeasurements, and the bandwidth associated with the RTT measurement(e.g., with higher bandwidths considered to have lower error). In somecases, the WLS multilateration algorithm may also consider, otherinformation (e.g., RSS, angle of arrival (AoA), etc.), applying weightsthereto based on uncertainty (e.g., higher weights to RSS measurementssince RSS may have high uncertainty than RTT). At step 450, thecloud-based location platform updates the beacon database to include thedetermined position of the beacon 140, or more specifically thedetermined physical antenna position of the beacon. Thereafter, portions(e.g., tiles) of the updated beacon database 170 may be provided back toUE 110, such that the determined physical antenna position of the beaconcan be used in RTT-based positioning of UE.

Accuracy of the trilateration often may be improved by using determinedpositions of UE that have very good position confidence. In the casewhere the determine position is a GNSS position fix, very good positionconfidence may be measured as very low HPE. FIG. 5 is a diagram of anexample arrangement 500 of UE 110 illustrating HPE and its use as anindicia of accuracy of a position determination. The position of beacon510 may be determined by a trilateration that uses the GNSS position fixof UE 520-540, which each have an HPE represented by a circle having agiven radius. In particular, the HPE of UE 540 is somewhat large,indicating there is low confidence in this position. The position of UE540 may be very inaccurate, which could be affecting accuracy of thetrilateration. If the accuracy of the position of UE 540 could beimproved, accuracy of the trilateration could likely also be improved.

One technique to improve accuracy of the position determination for UE110 involves a RTK correction service. In a traditional implementation“on board” implementation of RTK correction, the GNSS receiver 130 inthe UE 110 is RTK capable and interacts with an independent network ofRTK base stations that provide real time corrections that are applied atthe UE. However, RTK capable GNSS receivers are generally quiteexpensive and are not commonly deployed in low-cost UE (e.g.,smartphones, smartwatches, etc.). Accordingly, if operations arerestricted to being “on board”, many UE 110 cannot obtain the benefitsof RTK correction.

This limitation may be addressed by an “off-board” implementation wherethe raw GNSS measurements (e.g., pseudoranges) from the UE 110 areprovided to the cloud-based location platform 160, which performs theRTK GNSS position fix. FIG. 6 is a flow diagram detailing exampleoperations 600 performed by the cloud-based location platform 160 in an“off-board” implementation to determine beacon position, or morespecifically beacon physical antenna position, using a cloud-based RTKGNSS position fix. At step 610, the cloud-based location platform 160receives observations from UE 110 of RTT capable beacons. Theobservations may include one or more sets of raw GNSS measurements(e.g., pseudoranges) from the GNSS receiver 130 of the UE 110, anidentifier of the beacon (e.g., MAC address, cell ID, etc.) and RTTinformation. The RTT information may include a RTT measurement, a RTTmeasurement uncertainty, a signal strength associated with the RTTmeasurement, a bandwidth associated with the RTT measurement, as well asother RTT-related data. At step 620, the cloud-based location platform160 connects to a RTK correction service via the Internet 150 andobtains RTK correction information. At step 630, for each set of rawGNSS measurements the cloud-based location platform 160 determines acorrected GNSS position fix for the UE 110 using the raw GNSSmeasurements and the RTK correction information. At step 640, thecloud-based location platform 160 determines HPE of the resultingcorrected GNSS position fix for each of the UE 110. This corrected GNSSposition fix generally will have a much lower HPE than a GNSS positionfix produced by UE themselves.

At step 650, the cloud-based location platform 160 aggregatesobservations, including the cloud-based RTK GNSS position fixes of UE,for a given beacon. At step 660, the cloud-based location platform 160filters out observations based on a comparison of the HPE of the GNSSposition fix with a threshold. At step 670, the cloud-based locationplatform 160 uses a trilateration algorithm to determine to beaconposition, or more specifically beacon physical antenna position, basedon the aggregated observations from the UE 110. The trilaterationalgorithm may be a WLS multilateration algorithm with weights asdescribed above, with the exception that HPE of the corrected GNSSposition fix is used instead of HPE from the UE 110. At step 680, thecloud-based location platform 160 updates the beacon database 170 toinclude the determined position of the beacon 140, or more specificallythe determined physical antenna position of the beacon. Thereafter,portions (e.g., tiles) of the updated beacon database 170 may beprovided back to UE.

The portions (e.g., tiles) of the updated beacon database 170 may belocally cached and used by UE 110 to perform RTT-based positioning. Anumber of different RTT-based positioning algorithms may be used thatbase the position determination solely on RTT measurements, or that useRTT in combination with other information (e.g., RSS, AoA, etc.). In oneembodiment, a hybrid RTT-based positioning algorithm is utilized thathybridizes a WLS positioning algorithm and an extended Kalman filterpositioning algorithm.

FIG. 7 is a flow diagram detailing example operations 700 performed by apositioning client 122 on a UE 110 to implement a hybrid RTT-basedpositioning algorithm to determine UE position. At step 710, thepositioning client 122 aggregates RTT measurements by RTT capablebeacons in range of the UE 110 over a period of time (e.g., a one secondperiod). At step 720, the positioning client 122 determines a number ofunique beacons 140 in the aggregation for which information (e.g.,beacon positions) are available in portions (e.g., tiles) of the beacondatabase 170 locally cached by the UE 110. At step 730, the positioningclient 122 determines whether the number of unique beacons is greaterthan a threshold (e.g., one beacon). If the number of unique beacons isgreater than the threshold, execution proceeds to step 740, where UEposition is determined by a WLS positioning algorithm. The weights usedin the WLS positioning algorithm may be based on the number of RTTmeasurements, confidence of the determined position of the beacons(e.g., HPE), RTT measurement uncertainty, and/or other factors. A WLSposition uncertainty (e.g., a WLS position HPE) may also be produced aspart of step 740. At step 745, the positioning client 122 resets andinitializes Kalman filter state to be equal to the determined WLSposition. Then, at step 750, the positioning client 122 reports thedetermined WLS position as the position of the UE 110 (e.g., to anapplication executing on the UE).

If the number of unique beacons is not greater than the threshold,execution proceeds to step 760, where UE position is determined by aKalman filter positioning algorithm. If Kalman filter state werepreviously initialized to be equal to the determined WLS position aspart of step 745, such initialization is used. If not, Kalman filterstate may be initialed to a median beacon location of the uniquebeacons. At step 770, the positioning client 122 determines whether theKalman filter positioning algorithm was successful, and if so, at step750, the positioning client 122 reports the determined Kalman positionas the position of the UE 110. If the Kalman filter positioningalgorithm was not successful, at step 775, the positioning client 122determines whether there was a prior Kalman position returned within afreshness interval (e.g., 2 seconds), and if so, at step 750, thepositioning client 122 reports the prior Kalman position as the positionof the UE 110 (e.g., to an application executing on the UE). If therewas no prior Kalman position returned within the freshness interval, atstep 780, the positioning client 122 determines whether there was aprior WLS position returned within the freshness interval. If so, atstep 750, the positioning client 122 resets and initializes Kalmanfilter state to be equal to the prior WLS position at step 790 reportsthe prior WPS position as the position of the UE 110, and at step 750.If there was no prior WLS position returned within the freshnessinterval, at step 795, the positioning client 122 reports no positionresult for the UE 110.

It should be understood that in addition to basing positiondetermination solely on RTT measurements, positioning algorithms may useRTT in combination with other information (e.g., RSS, AoA, etc.) todetermine position. In some cases, RTT measurements may be used toimprove accuracy of techniques that primarily utilizes another form ofbeacon data (e.g., RSS). For example, a positioning algorithm may usemultiple RSS measurements for beacons in a weighted trilateration toestimate UE position. RTT measurements may be used to adjusts the RSSmeasurements, filter out potentially erroneous RSS measurements, adjustweights assigned to beacons in the weighted trilateration and/or inother manners to improve the accuracy of the RSS positioning.

The above description details various crowd sourcing techniques toenable RTT-based positioning of UE 110. It should be understood that thetechniques and portions thereof may be utilized together, individually,or in combination with other techniques, depending on theimplementation. Further, it should be understood that aspects of thetechniques may be modified, added to, removed, or otherwise changeddepending on the implementation. Further, while specific examplehardware and software is discussed above, it should be understood thatthe techniques may be implemented using a variety of different types ofhardware, software, and combination thereof. Such hardware may include avariety of types of processors, memory chips, programmable logiccircuits, application specific integrated circuits, and/or other typesof hardware components that support execution of software. Such softwaremay include executable instructions that implement applications storedin a non-transitory electronic device-readable medium, such as avolatile or persistent memory device, a hard-disk, or other data store.Combinations of software and hardware may be adapted to suit differentenvironments and applications. Above all, it should be understood thatthe above descriptions are meant to be taken only by way of example.

What is claimed is:
 1. A method to enable round-trip time (RTT)-basedpositioning, comprising: scanning, by a wireless network interface ofuser equipment (UE) for beacons within range of the UE; accessinginformation from a beacon database maintained by a cloud-based locationplatform to determine whether RTT capabilities are known for each beaconwithin range of the UE; sending, for one or more beacons having unknownRTT capabilities, range requests to attempt to have the beacon measureRTT, and based thereon assigning the beacon a RTT measurement statusthat indicates the beacon's RTT capabilities; uploading at least the RTTmeasurement status to the cloud-based location platform to update thebeacon database, such that the UE both consumes information regardingRTT capabilities of beacons from the beacon database, and contributesinformation regarding RTT capabilities of beacons to the beacondatabase.
 2. The method of claim 1, wherein the beacons are Wi-Fi accesspoints (APs) and the RTT capabilities include support for fine timingmeasurement (FTM) protocol according to a Institute of Electrical andElectronics Engineers (IEEE) 802.11mc standard.
 3. The method of claim1, wherein the beacons are cellular base stations, the RTT capabilitiesinclude support for 3rd Generation Partnership Project (3GPP) Release16, and the RTT is multi-RTT.
 4. The method of claim 1, wherein thescanning is performed in response to a present request to determineposition of the UE.
 5. The method of claim 1, wherein the scanning isperformed as a background process independent of any present request todetermine position of the UE.
 6. The method of claim 1, furthercomprising: downloading a local copy of a portion of the beacon databasethat covers a geographic area including a present position of the UE,the beacon database identifying beacons as being RTT capable, RTTincapable or having unknown RTT capabilities and wherein the accessingfurther comprises checking each beacon within range of the UE againstthe local copy.
 7. The method of claim 5, further comprising adding eachbeacon within range of the UE that is RTT capable or has unknown RTTcapabilities to a range list, and wherein the sending sends rangerequests to attempt to measure RTT with each beacon on the range list.8. The method of claim 1, further comprising: determining position ofthe UE using RTT-based positioning.
 9. The method of claim 1, furthercomprising: adding the RTT measurement status to a local cache, andwherein the uploading further comprises periodically sending contents ofthe local cache to the cloud-based location platform for inclusion in anupdate the beacon database.
 10. A method to enable round-trip time(RTT)-based positioning, comprising: providing, by a cloud-basedlocation platform to a plurality of user equipment (UE), informationregarding RTT capabilities of beacons from a beacon database, at leastone of the beacons initially having unknown RTT capabilities; receiving,by the cloud-based location platform, RTT information including at leastRTT measurement status from one or more of the plurality UE that haveattempted to measure RTT with a beacon of the beacons initially havingunknown RTT capabilities; determining RTT capabilities of the beaconbased on the received RTT measurement status; and updating the beacondatabase to include information indicating the RTT capabilities of thebeacon; such that the cloud-based location platform both providesinformation regarding RTT capabilities of beacons from the beacondatabase that are consumed by the one or more UE, and receiveinformation regarding RTT capabilities of beacons contributed to thebeacon database from the one or more UE.
 11. The method of claim 10,wherein the beacons are Wi-Fi access points (APs) and the RTTcapabilities include support for fine timing measurement (FTM) protocolaccording to a Institute of Electrical and Electronics Engineers (IEEE)802.11mc standard.
 12. The method of claim 10, wherein the beacons arecellular base stations, the RTT capabilities include support for 3rdGeneration Partnership Project (3GPP) Release 16, and the RTT ismulti-RTT.
 13. The method of claim 10, wherein the determiningcomprises: marking the beacon is RTT capable if the measurement statusfrom at least one of the one or more UE indicates the UE has been ableto have the beacon measure RTT, marking the beacon as RTT incapable ifthe RTT measurement status from all of the one or more UE indicate theUE have been unable to have the beacon measure RTT, and marking thebeacon as having unknown RTT capabilities if the RTT measurement statusfrom at least one of the one or more UE indicates the UE is out of rangeto measure RTT and the RTT measurement status from all other of the oneor more UE indicates the UE have been unable to have the beacon measureRTT.
 14. The method of claim 10, further comprising: in response to theRTT capabilities of the beacon indicating that the beacon is RTTcapable, estimating an RTT bias for the beacon that measures an expectederror in RTT measurements by the beacon, and wherein the updatingcomprises adding information indicating the RTT bias for the beacon tothe beacon database.
 15. The method of claim 14, wherein the estimatingcomprises: computing a delta for a distance between a UE and the beaconcomputed based on RTT and a distance between the UE and the beaconcomputed based on a determined position of the UE position and anestimated position of the beacon, and determining the RTT bias of thebeacon based on the delta.
 16. The method of claim 14, wherein theestimating comprises: determining one or more other beacons that share acommon organization identifier with the beacon; and determining the RTTbias of the beacon based on an RTT bias of the one or more otherbeacons.
 17. The method of claim 10, further comprising: in response tothe RTT capabilities of the beacon indicating that the beacon is RTTcapable, determining whether a distance between a UE and the beaconcomputed based on RTT is consistent with a determined position of theUE, and if the distance is not consistent updating the RTT capabilities.18. The method of claim 10, further comprising: determining physicalantenna position of the beacon by a trilateration algorithm that usesRTT measurements from the plurality of UE, and wherein the updatingincludes adding the physical antenna position of the beacon to thebeacon database.
 19. The method of claim 10, wherein the determining RTTcapabilities and updating the beacon database are performed periodicallyaccording to a batch period.
 20. A method to enable round-trip time(RTT)-based positioning, comprising: receiving, by a cloud-basedlocation platform that maintains a beacon database, observations from aplurality user equipment (UE) that have observed a beacon, theobservations including at least a determined position of the UE and aRTT measurement for the UE by the beacon; using, by the cloud-basedlocation platform, a trilateration algorithm to determine physicalantenna position of the beacon based on the determined position and theRTT measurement of each of the plurality of UE; updating the beacondatabase to include the determine physical antenna position of thebeacon; providing, by the cloud-based location platform, the physicalantenna position of the beacon to one or more of the plurality of UE,such that the one or more UE both contribute information used todetermine physical antenna position of the beacon to build the beacondatabase and consume physical antenna position of the beacon from thebeacon database.
 21. The method of claim 20, wherein the beacons areWi-Fi access points (APs) and the RTT capabilities include support forfine timing measurement (FTM) protocol according to a Institute ofElectrical and Electronics Engineers (IEEE) 802.11mc standard.
 22. Themethod of claim 20, wherein the beacons are cellular base stations, theRTT capabilities include support for 3rd Generation Partnership Project(3GPP) Release 16, and the RTT is multi-RTT.
 23. The method of claim 20,wherein the determined position of the UE includes a position confidenceof the determined position, and the method further comprises: filteringout observations based on a comparison of the position confidence of thedetermined position of the UE with a threshold.
 24. The method of claim23, wherein the determination by the trilateration algorithm is furtherbased on the position confidence of a determined position.
 25. Themethod of claim 20, wherein the RTT information from the plurality of UEincludes a RTT measurement uncertainty, a signal strength associatedwith the RTT measurement and a bandwidth associated with the RTTmeasurement, and the determination by the trilateration algorithm isfurther based on the RTT measurement uncertainty, the signal strengthand the bandwidth for the plurality of UE.
 26. The method of claim 20,wherein the trilateration algorithm is a weighted least square (WLS)multilateration algorithm.
 27. The method of claim 20, wherein theinformation describing a position of the UE includes raw globalnavigation satellite system (GNSS) measurements for the UE and themethod further comprises: obtaining, by the cloud-based locationplatform from a Real Time Kinematic (RTK) correction service RTKcorrection information for the raw GNSS measurements of each UE; anddetermining, by the cloud-based location platform, a corrected GNSSposition fix for each UE using the raw GNSS measurements and the RTKcorrection information, wherein the information describing the positionand the RTT used by the trilateration algorithm includes the correctedGNSS position fix for each UE.
 28. The method of claim 27, furthercomprising: determining a horizontal positioning error (HPE) of thecorrected GNSS position fix for the plurality of UE, and wherein thedetermination by the trilateration algorithm is further based on the HPEof the corrected GNSS position fix for the plurality of UE.
 29. Anon-transitory electronic device readable media having software storedthereon, the software when executed on one or more processors of one ormore electronic devices operable to: receive a round-trip time (RTT)measurement from a plurality of user equipment (UE) that have attemptedto measure RTF with a beacon initially having unknown RTT capabilities;determine the beacon is RTT capable and a position of the beacon basedon the RTT measurement from the plurality of UE; update a beacondatabase to include information indicating the beacon is RTT capable andthe determined position of the beacon; and provide information includingan indication the beacon is RTT capable and the determined position ofthe beacon to at least one UE as part of a set of beacon information fora geographic area usable to estimate position of the UE.
 30. Thenon-transitory electronic device readable media of claim 29, wherein thebeacons are Wi-Fi access points (APs) and a beacon is RTT capable whenit supports fine timing measurement (FTM) protocol according to aInstitute of Electrical and Electronics Engineers (IEEE) 802.11mcstandard.
 31. The non-transitory electronic device readable media ofclaim 29, wherein the beacons are cellular base stations, the RTTcapabilities include support for 3rd Generation Partnership Project(3GPP) Release 16, and the RTT is multi-RTT.
 32. The non-transitoryelectronic device readable media of claim 29, wherein the beacon isdetermined RTT capable in response to at least one of the plurality ofUE having been able to have the beacon measure RTT.
 33. Thenon-transitory electronic device readable media of claim 29, wherein thesoftware is further operable to: estimate an RTT bias for the beaconthat measures an expected error in RTT measurements by the beacon, andadd information indicating the RTT bias for the beacon to the beacondatabase.
 34. The non-transitory electronic device readable media ofclaim 29, wherein the software is further operable to: determine thedistance between each UE and the beacon computed based on RTT isconsistent with a determined position of the UE.
 35. The non-transitoryelectronic device readable media of claim 29, wherein the software isfurther operable to: determine physical antenna position of the beaconby a trilateration algorithm that uses RTT measurements from theplurality of UE, and add the physical antenna position of the beacon tothe beacon database.
 36. A non-transitory electronic device readablemedia having software stored thereon, the software when executed on oneor more processors of one or more electronic devices operable to:receive information from a plurality of user equipment (UE) that haveobserved a beacon including at least raw global navigation satellitesystem (GNSS) measurements for the UE and a RTT measurement for the UEby the beacon; obtain from a Real Time Kinematic (RTK) correctionservice RTK correction a information for the raw GNSS measurements ofeach UE; determine a corrected GNSS position fix for each UE using theraw GNSS measurements and the RTK correction information; determineposition of the beacon based on the corrected GNSS position fix and theRTT measurement of each of the plurality of UE; update a beacon databaseto include the determine physical antenna position of the beacon; andprovide the physical antenna position of the beacon to one or more ofthe plurality of UE.
 37. The non-transitory electronic device readablemedia of claim 36, wherein the beacons are Wi-Fi access points (APs) anda beacon is RTT capable when it supports fine timing measurement (FTM)protocol according to a Institute of Electrical and ElectronicsEngineers (IEEE) 802.11mc standard.
 38. The non-transitory electronicdevice readable media of claim 36, wherein the beacons are cellular basestations, the RTT capabilities include support for 3rd GenerationPartnership Project (3GPP) Release 16, and the RTT is multi-RTT.
 39. Thenon-transitory electronic device readable media of claim 36, wherein thesoftware when executed is further operable to: determine a horizontalpositioning error (HPE) of the corrected GNSS position fix for theplurality of UE, and wherein position determination of the beacon uses atrilateration algorithm that is based at least in part on the HPE of thecorrected GNSS position fix for the plurality of UE.
 40. Thenon-transitory electronic device readable media of claim 36, wherein thetrilateration algorithm is a weighted least square (WLS) multilaterationalgorithm.